fix(ci): explain the missing yank scope instead of a bare 403 - #9
Merged
Conversation
The yank run failed with 403 Forbidden: this token does not have the required permissions because crates.io scopes yanking separately from publishing — a token with publish-new + publish-update, which is what releases this crate, cannot yank it. The raw error never says which scope is missing, so the next person hits the same wall. Now it names the scope, the page to fix it on, and the fact that the release scopes need keeping if it is the same token.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The yank run failed:
crates.io scopes yanking separately from publishing. The
CARGO_REGISTRY_TOKENsecret haspublish-new+publish-update— which is exactly what's needed to release the crate, and not enough to yank it. The raw error never says which scope is missing, so the next person hits the same wall.The step now detects that specific failure and prints the scope, the page to fix it on, and a note to keep the publish scopes if it's the same token.
To actually run the yanks: add the
yankscope at https://crates.io/settings/tokens (keepingpublish-new+publish-update), update theCARGO_REGISTRY_TOKENsecret, then: